Platform and software framework for data intensive applications in the cloud

ABSTRACT

A system deploys visualization tools, business analytics software, and big data software in a multi-instance mode on a large, coherent shared memory many-core computing system. The single machine solution provides or high performance and scalability and may be implemented remotely as a large capacity server (i.e., in the cloud) or locally to a user. Most big data software running in a single instance mode has limitations in scalability when running on a many-core and large coherent shared memory system. A configuration and deployment technique using a multi-instance approach, which also includes visualization tools and business analytics software, maximizes system performance and resource utilization, reduces latency and provides scalability as needed, for end-user applications in the cloud.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the priority benefit of U.S. Provisional Patent Application Ser. No. 61/818,288, titled “Platform and Software Framework for Data-Intensive Applications in the Cloud,” filed May 1, 2013, and the priority benefit of U.S. Provisional Application Ser. No. 61/841,262, titled “Platform and Software Framework for Data-Intensive Applications in the Cloud,” filed Jun. 28, 2013, the disclosures of which are incorporated herein by reference.

BACKGROUND

1. Field of the Invention

The present invention generally relates to executing application software that process big data. More specifically, the present invention relates to implementing big data software in a single multi-instance node.

2. Description of the Related Art

Applications software that process big data tend to stress system resources with a large load. To deal with this, big data applications are often run on multiple machines. When multiple copies of big data software are running on multiple machines, they can process large amounts of data more quickly than only one such machine.

Processing big data on multiple machines has disadvantages. When multiple machines execute multiple copies of big data software, the software copies often need to communicate with each other. These multiple machines each have an IP address and communicate over a network such as the Internet. Communication between machines over a network, wherein each machine has its own IP address, inherently will introduce delays due to network latency. Additional steps for data aggregation across the network to deliver the ultimate result to end users in the cloud, incur further delays.

FIG. 1 is a block diagram of a cluster of nodes of the prior art. The cluster of nodes includes nodes 1-6. Each node may include memory, a processor with one or more cores, and other computing components. When processing large amounts of data, a copy of a big data software application may execute on each node. Different copies of the same software may be loaded onto and executed by each node in order to achieve faster processing of large amounts of data. The nodes each have their own IP address and communicate with each other over one or more networks such as the Internet, which introduces latency in the processing of the data.

The delay in processing data and aggregating the result set by big data software for end users in the cloud degrades performance of the big data software and may even cause errors due to latency. What is needed is an improved method for processing data by big data software for end-user applications in the cloud.

SUMMARY

A system is provided for deploying visualization tools, business analytics software, and big data software in a multi-instance mode on a large, coherent shared memory many-core computing system. The single machine solution provides high performance and scalability and may be implemented remotely as a large capacity server (i.e., in the cloud) or locally to a user. Most big data software running in a single instance mode has limitations in scalability when running on a many-core and large coherent shared memory system. A configuration and deployment technique using a multi-instance approach, which also includes visualization tools and business analytics software, maximizes system performance and resource utilization, reduces latency and provides scalability as needed for end-user applications in the cloud.

In embodiments, a method for visualizing data may instantiate a number of application instances on a multi-core single machine. Analytics may be performed by one or more of the application instances on data from a database implemented on the single machine. Visualization data may be provided based on the analytics by a visualization application implemented on the same machine.

A multi-core single machine for visualizing data may include a processor, memory, and one or more modules stored in memory. The one or more modules may be executable by the processor to instantiate a number of application instances on the multi-core single machine, perform analytics by one or more of the application instances on data from a database implemented on the single machine, and provide visualization data based on the analytics by a visualization application implemented on the same machine.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a cluster of nodes of the prior art.

FIG. 2 is a block diagram of a machine having a many-core shared memory system, business layer, and visualization layer.

FIG. 3 is a block diagram of a system having a high number of cores.

FIG. 4 is a method for configuring and providing visualization by a many-core single machine.

FIG. 5 is a method for deploying software in a multi-instance node.

FIG. 6 is a block diagram for providing a visualization capability by a visualization tool based on retrieved data.

FIG. 7 is a block diagram of an exemplary computing device for implementing the present technology.

DETAILED DESCRIPTION

The present system provides for deploying visualization tools, business analytics software, and big data software in a multi-instance mode on a large, coherent shared memory many-core computing system. The single machine solution provides high performance and scalability and may be implemented remotely as a large capacity server (i.e., in the cloud) or locally to a user. Most big data software running in a single instance mode has limitations in scalability when running on a many-core and large coherent shared memory system. A configuration and deployment technique using a multi-instance approach, which also includes visualization tools and business analytics software, maximizes system performance and resource utilization, reduces latency and provides scalability as needed by end-user applications in the cloud.

FIG. 2 is a block diagram of a machine having a many-core shared memory system, business layer, and visualization layer. The single machine 200 of FIG. 2 includes hardware layer 210, cloud management software 220, virtual machine layer 230, middleware 240 and visualization layer 250. The hardware layer 210 may include many cores and a shared memory system. The many core shared memory system may be configured to receive and execute multiple instances of client applications, for example on cloud management software 220.

Cloud management software 220 may include software for configuring application instances and ingesting data for one or more of the application instances. Instance configuration module 224 may be executed to configure application instances on machine 200. Data loading module 22 may be executed to ingest large amounts of data in parallel on machine 200. Configuring application instances and ingestion of data is discussed in more detail below with respect to FIGS. 4 and 5.

Virtual machine layer 230 may implement one or more virtual machines on machine 200. The virtual machine engine 230 may include a database engine 232, which may be implemented as a graph database. The graph database may manage data that can be accessed by one or more client applications for analytics and eventual visualization.

Middleware layer 240 may include one or more client applications that access data from database engine 232, perform analytics on the data, and provide data for visualization to visualization layer 250. In some embodiments, middleware layer 240 may include information management software 244 and business intelligence application 242. Software 244 and 242 may collectively provide an application server and framework for use for enterprise and web development, message queuing, memory management for concurrent users, security, and container management. The software may also include an open source library for in-database analytics over unstructured and structured data, an open source mining framework with data extracted from a backend database, and an open source in-memory complex event processing (CEP) engine to process machine generated/sensor data.

Visualization layer 250 may receive one or more data streams from one or more applications of the middleware layer and provide visualization data based on the received data. Visualization layer may include adaptor module 252. The adaptor module may be used to adapt data received from multiple data sources in a variety of formats and adapt the data to a particular format. By adapting the data to a single format, data from a plurality of sources and business sectors may be visualized.

The machine 200 of FIG. 2 provides a software development framework implemented on a large, coherent shared memory system enabled over a network (i.e., in the “cloud”). The implementation may use a kernel based virtual machine (KVM) and be supported by cloud management software. Multiple virtual machines of large sizes may be created as a process for efficiently provisioning resources of the large, coherent shared memory system. One or more applications that run on multiple virtual machines of the shared memory system “in the cloud” may be able to efficiently leverage the resources of the shared memory system for scalability and elasticity.

FIG. 3 is a block diagram of a system having a high number of cores. The layers of machine 200 may be implemented on hardware such as the system of FIG. 3.

The machine 300 includes a plurality of sockets 310. Each socket may include a plurality of cores 320. For example, the system 300 may include 128 sockets, with each socket including 15 cores, for a total of 1,920 cores. The sockets may each include multiple memory DIMM slots, such as for example, 12 memory DIMM slots each populated with 32 GB DIMMs providing a total of 48 TB system memory.

The cores of each socket may be grouped into an instance which processes a software application. For example, the cores of a particular socket may form one or more instances, and cores from multiple adjacent sockets may form an instance. The instances may be formed from a number of cores and memory such that they are able to host and execute a software instance as efficiently as possible.

FIG. 4 is a method for configuring and providing visualization by a many-core single machine. Application instances may be configured on a single machine at step 410. The application instances can be configured to provide as many instances as possible and/or as needed for efficient handling of analytics. The application instances may be instantiated in the middleware layer of the single machine 200. More detail for configuring and providing visualization by a many-core single machine is discussed with respect to the method of FIG. 5.

Analytics are performed on the single machine at step 420. Once the application instances are configured and data is ingested, the client applications may perform analytics on data stored in the machine. Because the data and middleware is on the same machine, there analytics may be performed quickly and efficiently.

A visualization of the analytic results may be provided by the single machine at step 430. Once the analytics become available, a data stream may be provided to the visualization layer on the same machine on which the analytics take place. The visualization layer includes a visualization tool which may generate a graphical interface for the data.

The present system may adapt a data stream from a first format into a second format. The adapted data in the second format may be placed in a template, such as a Java template, and then accessed by the visualization tool. Because the visualization is provided by the same machine as the analytics software and application instances, the visualization may be performed quickly and without latency inherent in systems that have these software packages distributed over two or more machines.

The visualization may be viewed through a remote device, such as a desktop computer, workstation or a mobile device. The mobile device, such as for example a smart phone, may include an application stored and executing on the smart device and configured to receive a graphical interface generated by the visualization layer.

FIG. 5 is a method for deploying software in a multi-instance node. First, application requirements of a system memory and the number of CPU cores are identified at step 510. This step may help determine whether the application is memory intensive, CPU intensive, or both.

Application requirements for memory usage may be determined by performing a test of the system on which the application instances will be deployed. An automated testing application (such as instance a configuration module), user, or combination of both may run a workload/benchmark test using a single instance of the application on a system. The test may execute for a period of time, for example an hour, until the application reaches a steady state. The memory usage may then be stored once the application has reached the steady state. For example, a benchmark application may include a UNIX system-related command such as “SAR” or other command to retrieve the memory usage at the desired state.

The number of CPU cores to utilize may be determined by performing a test of the system on which the application instances will be deployed. An automated testing application, user, or combination of both may run a workload/benchmark test using a single instance of the application system. The application may determine whether CPU usage by the instance is just above a certain threshold, such as for example above 85%. If CPU usage falls below the threshold, then more cores are being utilized then needed or desired, and the test may be repeated or continued with a lower number of cores. For example, while running the test, a command such a NUMA command may be issued to reduce the number of cores for the single application instance until the application requires 85% of the allocated cores. For instance, on a UV system with 128 cores, if 16 cores are allocated to the application instance, then CPU usage should be around 12% (out of 128 cores).

The number of application instances may be determined at steps 520. The instances may be the lesser of the ratio of total memory to memory usage and the ratio of total cores to used cores. The ratio of total memory to memory usage may be determined as the total memory in the system divided by the memory used by the application in the steady state. The core ratio may be determined by dividing the total number of cores in the system to the number of cores required to run a single application at less than a threshold value (e.g., 85%). Both ratios may be determined by an application stored in memory and executed by a processor of the present system, such as a testing application. The lesser of the two ratio values is taken as the number of application instances.

The application instances may be deployed at step 530. The application instances may be installed on the system and executed to process multiple subsets of cores and memory. In some embodiments, the multiple instances may be executed by a multi-threaded program to ensure they are started (or terminated) at about the same time when data is processed.

The instance configuration module may ensure that each instance is invoked with an allocation of cores and memory space. For example, instance configuration module 230 executing on a multi-instance computing system may issue NUMA commands to allocate the core count and memory size allocated to each instance of the application.

To optimize the performance from a single application instance, several steps may be taken by the application. For example, the cores and memory may be allocated from within the same NUMA nodes. Alternatively, the cores and memory may be allocated from adjacent NUMA nodes. The application may set a memory policy to be local or allocate cores from local memory of a NUMA node or adjacent NUMA nodes if an application requires memory policy as “interleave.”

Once the instances are deployed, data may be loaded into the application instances for processing at step 540. Data may be loaded into each instance in parallel, based on CPU performance, to provide the data for processing more quickly. The data may be identified via files for loading into each instance.

For example, after estimating a database size, the database size is divided by a core count. The core count may be retrieved from step 520. A single load may be run, and a determination is made as to whether more than 85% of CPU usage is occurring. If not, the core count is reduced at step 535. Next, instances may be determined as the total core count divided by the determined core count. Data is then divided by the number of instances and a text file is created with a file name list for each core count at step 555. The text file is then input into the loading program. A localized database instance may then be allocated.

More details for deploying software in a multi-instance node are described in U.S. patent application Ser. No. 14/266,758, titled “Deploying Big Data Software in a Multi-Instance Node,” filed Apr. 30, 2014, the disclosure of which is incorporated herein by reference.

FIG. 6 is a block diagram for providing a visualization capability by a visualization tool based on retrieved data. First, a node start up display is determined for a graph database at step 610. A user may install and load the graph database software. The top node layer may be defined as the first node(s) that need to be displayed as soon as the graph is launched. If the graph has disconnected regions, the top nodes of the disconnected regions may be displayed. A query may be created using the database query language. In embodiments, all top display nodes may be returned in this query. A standard software programming model, such as for example a Keylines software programming model, may be used to display the top nodes.

Next, data is retrieved from the graph database at step 620. Retrieving data may include establishing a connection with a graph database, querying the graph database for the data, and then receiving and processing the stream of data received from the graph database by the adapter module.

To retrieve the data, a connect layer program may be implemented from the graph database to a visualization software. In embodiments, the query used within a J2EE program may be formatted to output a JSON conversion. For each node selection, the query and JSON conversion may be different. This can be done with one or more J2EE programs. The JSON conversion output must contain both the relationship and node value. It may contain properties if display is desired by a user. The connect layer will allow any graph database technology to connect to software such as Keylines visualization software.

A visualization capability is provided by the visualization tool based on the retrieved data at step 630. To provide the visualization, a hook to a graph database visualization tool may be created at step 130. A Keylines programming model may be used to hook the graph database visualization tool. JQuery or AJAX may be used to hook the JSON output from step 120 to Keylines. Javascript is recommended as the language to use for exterior Keylines web UI visualization.

More details for providing a visualization capability are described in U.S. patent application Ser. No. 14/266,656, titled “Software Design Pattern for Adapting a Graph Database Visualization,” filed Apr. 30, 2014, the disclosure of which is hereby incorporated herein by reference.

FIG. 7 illustrates an exemplary computing system 700 that may be used to implement all or a portion of a computing device for use with the present technology. For example, the computing system 700 may describe additional components for system 300 of FIG. 3 and a mobile device in communication with system 300. The computing system 700 of FIG. 7 includes one or more processors 710 and memory 720. Main memory 720 stores, in part, instructions and data for execution by processor 710. Main memory 720 can store the executable code when in operation. The system 700 of FIG. 7 further includes a mass storage device 730, portable storage medium drive(s) 740, output devices 750, user input devices 760, a graphics display 770, and peripheral devices 780.

The components shown in FIG. 7 are depicted as being connected via a single bus 790. However, the components may be connected through one or more data transport means. For example, processor unit 710 and main memory 720 may be connected via a local microprocessor bus, and the mass storage device 730, peripheral device(s) 780, portable storage device 740, and display system 770 may be connected via one or more input/output (I/O) buses.

Mass storage device 730, which may be implemented with a magnetic disk drive or an optical disk drive, is a non-volatile storage device for storing data and instructions for use by processor unit 710. Mass storage device 730 can store the system software for implementing embodiments of the present invention for purposes of loading that software into main memory 720.

Portable storage device 740 operates in conjunction with a portable non-volatile storage medium, such as a floppy disk, compact disk or Digital video disc, to input and output data and code to and from the computer system 700 of FIG. 7. The system software for implementing embodiments of the present invention may be stored on such a portable medium and input to the computer system 700 via the portable storage device 740.

Input devices 760 provide a portion of a user interface. Input devices 760 may include an alpha-numeric keypad, such as a keyboard, for inputting alpha-numeric and other information, or a pointing device, such as a mouse, a trackball, stylus, or cursor direction keys. Additionally, the system 700 as shown in FIG. 7 includes output devices 750. Examples of suitable output devices include speakers, printers, network interfaces, and monitors.

Display system 770 may include a liquid crystal display (LCD) or other suitable display device. Display system 770 receives textual and graphical information, and processes the information for output to the display device.

Peripherals 780 may include any type of computer support device to add additional functionality to the computer system. For example, peripheral device(s) 780 may include a modem or a router.

The components contained in the computer system 700 of FIG. 7 are those typically found in computer systems that may be suitable for use with embodiments of the present invention and are intended to represent a broad category of such computer components that are well known in the art. Thus, the computer system 700 of FIG. 7 can be a personal computer, hand held computing device, telephone, mobile computing device, workstation, server, minicomputer, mainframe computer, or any other computing device. When implemented as a device such as a smart phone, the system 700 may include additional components such as one or more antennas, radios, microphones, an LED touch screen, and other components. The computer can also include different bus configurations, networked platforms, multi-processor platforms, etc. Various operating systems can be used including Unix, Linux, Windows, Macintosh OS, Palm OS, and other suitable operating systems.

The foregoing detailed description of the technology herein has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the technology to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. The described embodiments were chosen in order to best explain the principles of the technology and its practical application to thereby enable others skilled in the art to best utilize the technology in various embodiments and with various modifications as are suited to the particular use contemplated. It is intended that the scope of the technology be defined by the claims appended hereto. 

What is claimed is:
 1. A method for visualizing data, comprising: instantiating a number of application instances on a multi-core single machine; performing analytics by one or more of the application instances on data from a database implemented on the single machine; and providing visualization data based on the analytics by a visualization application implemented on the same machine.
 2. The method of claim 1, wherein the application instances, database, and visualization application are implemented on the multi-core single machine that provides the visualization data to a client device over a network.
 3. The method of claim 1, wherein the client device is a smart phone, the visualization data displayed through an application residing on the smart phone.
 4. The method of claim 1, wherein the transfer of data from the database to the one or more application occurs only on the single machine and a transfer of analytic results by the one or more applications to the visualization application occurs only on the single machine.
 5. The method of claim 1, the method further comprising: determining a core-memory ratio for a single instance execution of an application; determining a number of instances of the application to deploy in a multi-instance database; and applying the optimal core-memory ratio to each instance.
 6. The method of claim 1, wherein the core-memory ratio is determined based on CPU usage.
 7. The method of claim 1, further comprising loading data into each instance in parallel.
 8. The method of claim 1, wherein the database on the single machine is graph database, the method further comprising: retrieving a data stream from the graph database; and populating a template from the data stream.
 9. The method of claim 1, further comprising: retrieving data from a database in a first format; adapting the retrieved data to a second format compatible with a visualization interface; and providing a visualization based on the retrieved data having the second format.
 10. A non-transitory computer readable storage medium having embodied thereon a program, the program being executable by a processor to visualize data, the method comprising: instantiating a number of application instances on a multi-core single machine; performing analytics by one or more of the application instances on data from a database implemented on the single machine; and providing visualization data based on the analytics by a visualization application implemented on the same machine.
 11. The non-transitory computer readable storage medium of claim 9, wherein the application instances, database, and visualization application are implemented on the multi-core single machine that provides the visualization data to a client device over a network.
 12. The non-transitory computer readable storage medium of claim 9, wherein the client device is a smart phone, the visualization data displayed through an application residing on the smart phone.
 13. The non-transitory computer readable storage medium of claim 9, wherein the transfer of data from the database to the one or more application occurs only on the single machine and a transfer of analytic results by the one or more applications to the visualization application occurs only on the single machine.
 14. The non-transitory computer readable storage medium of claim 9, the method further comprising: determining a core-memory ratio for a single instance execution of an application; determining a number of instances of the application to deploy in a multi-instance database; and applying the optimal core-memory ratio to each instance.
 15. The non-transitory computer readable storage medium of claim 9, wherein the core-memory ratio is determined based on CPU usage.
 16. The non-transitory computer readable storage medium of claim 9, further comprising loading data into each instance in parallel.
 17. The non-transitory computer readable storage medium of claim 9, wherein the database on the single machine is graph database, the method further comprising: retrieving a data stream from the graph database; and populating a template from the data stream.
 18. The non-transitory computer readable storage medium of claim 9, further comprising: retrieving data from a database in a first format; adapting the retrieved data to a second format compatible with a visualization interface; and providing a visualization based on the retrieved data having the second format.
 19. A multi-core single machine for visualizing data, comprising: a processor; memory; one or more modules stored in memory and executable by the processor to instantiate a number of application instances on the multi-core single machine, perform analytics by one or more of the application instances on data from a database implemented on the single machine, and provide visualization data based on the analytics by a visualization application implemented on the same machine.
 20. The multi-core single machine of claim 19, wherein the application instances, database, and visualization application are implemented on the multi-core single machine that provides the visualization data to a client device over a network.
 21. The multi-core single machine of claim 19, wherein the client device is a smart phone, the visualization data displayed through an application residing on the smart phone.
 22. The multi-core single machine of claim 19, wherein the transfer of data from the database to the one or more application occurs only on the single machine and a transfer of analytic results by the one or more applications to the visualization application occurs only on the single machine.
 23. The multi-core single machine of claim 19, the one or more modules further executable to determine a core-memory ratio for a single instance execution of an application, determine a number of instances of the application to deploy in a multi-instance database, and apply the optimal core-memory ratio to each instance.
 24. The multi-core single machine of claim 19, wherein the core-memory ratio is determined based on CPU usage.
 25. The multi-core single machine of claim 19, the one or more modules further executable to load data into each instance in parallel.
 26. The multi-core single machine of claim 19, wherein the database on the single machine is graph database, the method further comprising: retrieving a data stream from the graph database; and populating a template from the data stream.
 27. The multi-core single machine of claim 19, the one or more modules further executable to retrieve data from a database in a first format, adapt the retrieved data to a second format compatible with a visualization interface, and provide a visualization based on the retrieved data having the second format. 